Skip to content

Conversation

@matthiaskrgr
Copy link
Member

@matthiaskrgr matthiaskrgr commented Nov 18, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

matklad and others added 30 commits August 7, 2020 23:53
10: Allow type aliases in extern blocks r=jonas-schievink a=jonas-schievink

This is for the unstable feature rust-lang#43467, which rustc uses internally

Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
11: Allow both const & async modifiers
 r=matklad a=matklad

bors r+
🤖

Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
12: Fix .gitignore
 r=matklad a=matklad

bors r+
🤖

Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
I don't really look at the results of the benchmarks anyway, so having
them in the repo creates a false sense of benchmarkdness.

If I get to implementing proper benchmarking, I'd probably stay away
from criterion -- we need something much much simpler for this crate.
23: modernize r=matklad a=matklad



Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
The Travis workflow was deleted in 3d5b7e3476f91280aedda3900c13838b00d64a9d
…cros

Move towards upstream `macro_rules!` model
It's unclear if this is worthwhile, and this requires a lot of changes
in r-a
…ssert, r=oli-obk

debug-assert FixedSizeEncoding invariant

Something like this? It asserts during encoding that for that type, decoding 0 would give the default.
Preferably, I'd either somehow statically/in const assert it once, instead of every time, but I see no easy way to do so. It'd require us to iterate all types that implement the trait or something. Let me know what you think

No types currently violate this invariant.

r? `@oli-obk`
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rust-analyzer Relevant to the rust-analyzer team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Nov 18, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Nov 18, 2025

📌 Commit ceb33e9 has been approved by matthiaskrgr

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 18, 2025
@bors
Copy link
Collaborator

bors commented Nov 18, 2025

⌛ Testing commit ceb33e9 with merge 26e29af...

bors added a commit that referenced this pull request Nov 18, 2025
Rollup of 5 pull requests

Successful merges:

 - #147887 (Improve the documentation of atomic::fence)
 - #148281 (repr(transparent) check: do not compute check_unsuited more than once)
 - #148484 (Fix suggestion for the `cfg!` macro)
 - #149057 (`rust-analyzer` subtree update)
 - #149061 (debug-assert FixedSizeEncoding invariant)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors
Copy link
Collaborator

bors commented Nov 18, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Nov 18, 2025
@rust-log-analyzer
Copy link
Collaborator

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

@matthiaskrgr
Copy link
Member Author

@bors retry

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 18, 2025
@matthiaskrgr
Copy link
Member Author

matthiaskrgr commented Nov 18, 2025

@matthiaskrgr
Copy link
Member Author

@bors treeclosed-

@bors
Copy link
Collaborator

bors commented Nov 18, 2025

⌛ Testing commit ceb33e9 with merge 7c2c3c0...

@bors
Copy link
Collaborator

bors commented Nov 19, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 7c2c3c0 to main...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Nov 19, 2025
@bors bors merged commit 7c2c3c0 into rust-lang:main Nov 19, 2025
12 checks passed
@rustbot rustbot added this to the 1.93.0 milestone Nov 19, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#147887 Improve the documentation of atomic::fence 8501ec820887f003ca7030ad962ce5b73afd44be (link)
#148281 repr(transparent) check: do not compute check_unsuited more… f62f33aacbbfa33ac5f1c0b4c7ac58d03b5d4c3f (link)
#148484 Fix suggestion for the cfg! macro ae0ecb8218153e60b793d5d26aa5d6259d957110 (link)
#149057 rust-analyzer subtree update cbc73e357c09d6f1eb904324ddde17aa5c828638 (link)
#149061 debug-assert FixedSizeEncoding invariant 6f8a14f1c08b371746942d5c328c366b6675acbf (link)

previous master: 3d461af2a2

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@github-actions
Copy link
Contributor

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 3d461af (parent) -> 7c2c3c0 (this PR)

Test differences

Show 12 test diffs

12 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 7c2c3c0ded2de378bfab2f5b55c387c66fbaf353 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. aarch64-apple: 11367.7s -> 8633.8s (-24.0%)
  2. pr-check-1: 1974.5s -> 1673.2s (-15.3%)
  3. aarch64-gnu-llvm-20-2: 2630.2s -> 2249.7s (-14.5%)
  4. x86_64-rust-for-linux: 3035.3s -> 2608.9s (-14.0%)
  5. x86_64-gnu-gcc: 3580.4s -> 3079.5s (-14.0%)
  6. x86_64-gnu-tools: 3767.6s -> 3288.1s (-12.7%)
  7. armhf-gnu: 5651.2s -> 4934.7s (-12.7%)
  8. dist-x86_64-netbsd: 4509.7s -> 5070.1s (+12.4%)
  9. x86_64-gnu-llvm-20: 2784.6s -> 2451.0s (-12.0%)
  10. dist-aarch64-apple: 7460.7s -> 6582.1s (-11.8%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (7c2c3c0): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
0.1% [0.1%, 0.1%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (primary 2.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
2.7% [2.7%, 2.7%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.7% [2.7%, 2.7%] 1

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 473.417s -> 474.558s (0.24%)
Artifact size: 388.75 MiB -> 388.75 MiB (-0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rust-analyzer Relevant to the rust-analyzer team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.